Skip to content

Clarify backup/restore strategy regarding system db #2521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from

Conversation

NataliaIvakina
Copy link
Collaborator

No description provided.

@NataliaIvakina NataliaIvakina force-pushed the dev-backup-planning-improvement branch from a2314dc to c670af6 Compare August 15, 2025 06:38
Comment on lines 193 to 194
This option ensures that the backup includes not only `users` and `roles`, but also the cluster topology.
Cluster topology metadata, stored in the `system` database, defines the servers in the cluster and their operational modes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part is incorrect. Backing up a user database never backs up the topology, and it would be annoying if it did. 'all' does in fact just mean both 'users' and 'roles'.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the guidance about including metadata is in fact no different between clustered and standalone - if you want to backup your RBAC, include the metadata.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it looks like I misunderstood the card.
We can create a dump of the system database, but it won't help us to retain the cluster topology.

@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-2521.surge.sh

Updated pages:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants